Skip to main content

ContextMenu How To's

How to's for the ContextMenu guide.

How to Use ContextMenu?​

How to Use ContextMenu?​

The following steps explain how to create and use a ContextMenu object.

Add the ContextMenu Object to the Form​

  1. Open the form design screen
  2. Go to the Toolbox panel
  3. Find the ContextMenu object
  4. Drag and drop it onto the form

The ContextMenu is not visible on the form. This is expected behavior.

Define Menu Actions​

When the ContextMenu is selected, you can configure menu items in the Property Viewer panel:

  • Add Menu Items
  • For each menu item, define actions such as:
    • Open A Form
    • Open A Process
    • Start A Process
    • Execute Custom Action

Bind ContextMenu to DataGrid or TreeView​

  1. Select the DataGrid or TreeView object
  2. In the Properties panel, locate the ContextMenu field
  3. Select the ContextMenu object you created

Define Target Behavior​

The ContextMenu can be triggered on the following targets:

  • Container: Right-click anywhere in the grid
  • Row: Right-click only on a specific row

Usage in the Web Interface​

  • The user right-clicks on a DataGrid or TreeView
  • The defined ContextMenu is displayed
  • The selected menu item triggers the corresponding action

Usage Scenarios​

  • Opening a form from a row
  • Navigating to process details
  • Deleting or updating a record
  • Executing permission-based custom actions

Notes​

  • ContextMenu can access row-level data
  • Selected row data can be passed to actions as parameters
  • Preferred over toolbars when many row-based actions are required

How to Use Client Enabled?​

What is Client Enabled?​

Client Enabled is a property that defines whether a form control is active (enabled) on the client side when the form is first loaded.
If it is set to True, the control is immediately usable by the user.
If it is set to False, the control is disabled and cannot be interacted with until a specific condition or rule activates it.

This property is especially useful for controlling the user’s interaction flow and applying dynamic behaviors using the Rule Manager.

What Does It Do?​

The property allows developers to:

  • Control when a form control becomes interactive.
  • Prevent users from entering or changing data until prerequisites are met.
  • Dynamically enable or disable controls based on user input or logic.

Example Scenario — Conditional Activation​

Scenario:
A form contains a checkbox called “I Accept Terms” and a text field called “Signature.”
The goal is to make the “Signature” field inactive until the user checks “I Accept Terms.”

Steps to Implement:​

  1. Select the “Signature” field in the form editor.

  2. In the Properties panel, find the Client Enabled field.

  3. Set the value to False — the field will now be disabled by default when the form loads.

  4. Open the Rule Manager.

  5. Add a new rule:

    Condition:

Action:

  1. Save and publish the form.

Result:​

  • When the form loads, the “Signature” field is disabled.
  • Once the user checks “I Accept Terms,” the field automatically becomes active and editable.

Behavior Summary​

Property StateDescription
TrueThe control is active and ready for user interaction when the form loads.
FalseThe control is disabled at load time and can be enabled dynamically via rules or code.

Notes & Best Practices​

  • Use the Client Enabled property to manage client-side interactivity without requiring server actions.
  • Combine it with Rule Manager to define when and how controls become active.
  • Remember: if server enablement is disabled, the client cannot enable the control even if Client Enabled is set to True.
  • By default, this property is set to True (active).

Summary​

Client Enabled improves form usability by letting developers control when and how users interact with form controls.
It is essential for creating responsive, condition-based form experiences where user actions dynamically change the form’s state.

What Is ContextMenu?​

What Is ContextMenu?​

ContextMenu is a component used to define a context (right-click) menu that appears when the user performs a right-click action on table- or tree-based components such as DataGrid and TreeView.

Through this menu, users can:

  • Open a form
  • Start a process
  • View a process
  • Execute custom actions

When added to a form, ContextMenu does not appear on the UI by itself.
It becomes active only when it is associated with a DataGrid or TreeView component.

Where Is It Used?​

  • Creating right-click menus on DataGrid rows
  • Defining actions on TreeView nodes
  • Providing row-specific actions quickly to users
  • Offering advanced action options without cluttering the screen

Key Features​

  • Invisible (does not occupy space on the UI by itself)
  • Triggered via right-click
  • Supports multiple actions
  • Supports actions such as Open a Form, Open a Process, Start a Process
  • Can work at row level or container level

Notes​

  • The ContextMenu component does not work on its own
  • It must be bound to a DataGrid or TreeView component
  • Right-click behavior runs on the client side